|
Although in the past some differences existed between embedded Java and traditional PC based Java solutions, the only difference now is that embedded Java code in these embedded systems is mainly contained in constrained memory, such as flash memory. A complete convergence has taken place since 2010, and now Java software components running on large systems can run directly with no recompilation at all on design-to-cost mass-production devices (consumers, industrial, white goods, healthcare, metering, smart markets in general,...) Recent developments in the field are * In 2014, EBV annonced JAKARTA : a hardware & software application Java platform ready for new areas of low cost Human Machine Interfaces based on FREESCALE KINETIS-L (). * In October 2013, Renesas Electronics announced providing Embedded Java for RX Microcontrollers (). * In January 2013, STMicroelectronics announced full Java support for STM32 F3/F4-series microcontrollers STM32 and (stm32java ). * In March 2013, MicroEJ product line from IS2T for ARM Cortex-M (all RTOS), ARM Cortex-A (Linux, Integrity, VxWorks), ARM7-TDMI (all RTOS), ARM9 (Linux, Integrity), AVR32 UC3 (all RTOS), V850 (all RTOS). * Before 2012, the Squawk Virtual Machine, a JVM developed by Sun Microsystems and deployed as part of Project Sun SPOT. ==CORE embedded Java API for a unified Embedded Java ecosystem== In order for a software component to run on any Java system, it must target the core minimal API provided by the different providers of the embedded Java ecosystem. Companies such as Aplix, Google, IS2T, Myriad, Oracle, ... share the same eight packages of pre-written programs. The packages (java.lang, java.io, java.util, ... ) form the CORE Embedded Java API, which means that embedded programmers using the Java language can use them in order to make any worthwhile use of the Java language. 抄文引用元・出典: フリー百科事典『 ウィキペディア（Wikipedia）』 ■ウィキペディアで「Embedded Java」の詳細全文を読む スポンサード リンク
|